Skip to content

fix(cc-widgets): Add timeout inactivity properties to cc store#695

Open
zachraymer wants to merge 1 commit into
webex:nextfrom
zachraymer:next
Open

fix(cc-widgets): Add timeout inactivity properties to cc store#695
zachraymer wants to merge 1 commit into
webex:nextfrom
zachraymer:next

Conversation

@zachraymer

@zachraymer zachraymer commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

COMPLETES # https://jira-eng-sjc12.cisco.com/jira/browse/CAI-7907

This pull request addresses

Exposing the isTimeoutDesktopInactivityEnabled and timeoutDesktopInactivityMins properties on the agentConfig object from cc store

by making the following changes

adds the fields to the agentconfig object in the cc store and related types and adds unit tests

Change Type

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update
  • Tooling change
  • Internal code refactor

The following scenarios were tested

  • The testing is done with the amplify link
    < ENUMERATE TESTS PERFORMED, WHETHER MANUAL OR AUTOMATED >

The GAI Coding Policy And Copyright Annotation Best Practices

  • GAI was not used (or, no additional notation is required)
  • Code was generated entirely by GAI
  • GAI was used to create a draft that was subsequently customized or modified
  • Coder created a draft manually that was non-substantively modified by GAI (e.g., refactoring was performed by GAI on manually written code)
  • Tool used for AI assistance (GitHub Copilot / Other - specify)
    • Github Copilot
    • Other - Please Specify
  • This PR is related to
    • Feature
    • Defect fix
    • Tech Debt
    • Automation

Checklist before merging

  • I have not skipped any automated checks
  • All existing and new tests passed
  • I have updated the testing document
  • I have tested the functionality with amplify link

Make sure to have followed the contributing guidelines before submitting.

@zachraymer zachraymer requested review from brain-frog and cmullenx June 9, 2026 19:09
@zachraymer zachraymer requested a review from a team as a code owner June 9, 2026 19:09

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 258269f467

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment on lines +421 to +422
isTimeoutDesktopInactivityEnabled: profile.isTimeoutDesktopInactivityEnabled,
timeoutDesktopInactivityMins: profile.timeoutDesktopInactivityMins,

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Preserve timeout config when login payload omits it

When AGENT_STATION_LOGIN_SUCCESS or relogin payloads omit these optional fields (the existing station-login success fixture in packages/contact-center/station-login/tests/helper.ts has no timeout fields), setAgentProfile is invoked after registerCC and these assignments overwrite the timeout values that were just loaded from the registration Profile with undefined. Consumers reading store.agentProfile after login will lose isTimeoutDesktopInactivityEnabled/timeoutDesktopInactivityMins; only replace these keys when the payload actually includes them, or fall back to the existing values.

Useful? React with 👍 / 👎.

@aws-amplify-us-east-2

Copy link
Copy Markdown

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-695.d1b38q61t1z947.amplifyapp.com

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant